Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

launchProcedure

This procedure launches a business logic procedure or manager procedure. It determines if the procedure is already running and whether the existing instance should be replaced or a new instance run. If required, the procedure also connects to the AppServer partition. The procedure then updates the temp-table of running persistent procedures with the appropriate details.

Location: af\app\afsesmngrp.i

Parameters:

INPUT pcPhysicalName AS CHARACTER

The physical object filename, with path and extension.

INPUT plOnceOnly AS LOGICAL

If YES, then the procedure checks for an already running instance and uses it, if possible.

INPUT pcOnAppserver AS CHARACTER

Accepts values of YES, NO, or APPSERVER.

INPUT pcAppserverPartition AS CHARACTER

The AppServer partition name to run on.

INPUT plRunPermanent AS LOGICAL

The default is NO.

OUTPUT phProcedureHandle AS HANDLE

The procedure handle of object run.

Notes:

If the plRunPermanent flag is set to YES, then this procedure is not automatically killed when an AppServer agent is deactivated. Ordinarily this flag should be NO, and all procedures left running should be deleted at the end of an AppServer request by the deactivation routine. When procedures are closed down correctly, they are removed from the temp-table and deleted. This behavior tidies up any procedures started outside of this control procedure or shut down incorrectly for some reason.
If the pcOnAppserver flag is set to APPSERVER, then this procedure can only be run on AppServer. If the flag is YES and no AppServer partition is passed in, then it defaults to the AstraAppServer and the session handle, gshAstraAppserver handle, is used for the AppServer. If any other partition is passed in and the flag is not NO, then the partition is connected if required. Any partitions connected in this manner are disconnected by the shutdown procedure, af\sup2\afshutdwnp.p.
Generally, you do not need to run this procedure for most of the Progress Dynamics Managers because their handles are available through the systemwide global shared variables. However, in order to add the Managers to the temp-table of running persistent procedures, this procedure is used for the Managers when they are first run.
Examples: See the launchClassObject function in ry\app\ryrepmngrp.i.